Multicomputer processing of client device request data using centralized event orchestrator

ABSTRACT

Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator. A computing platform may receive event definition information defining an event as well as stimulus selection information. Subsequently, the computing platform may receive a request for a recipient-selection user interface. The computing platform may identify one or more stimulus options available for a user of a recipient computing device associated with the event and may send a delivery selection user interface that includes a user-selectable component, which, when invoked, causes the computing platform to create a new endpoint associated with a stimulus option. Thereafter, the computing platform may receive delivery selection information and may generate one or more event orchestration commands directing an event processor to execute one or more actions associated with the event. The computing platform then may send the one or more event orchestration commands to the event processor.

BACKGROUND

Aspects of the disclosure relate to electrical computers, digitalprocessing systems, and multicomputer data transferring. In particular,one or more aspects of the disclosure relate to multicomputer processingof client device request data using a centralized event orchestrator.

As computer systems are increasingly utilized to provide automated andelectronic services, such computer systems may obtain and maintainincreasing amounts of various types of sensitive information, andensuring the safety and security of this information may be increasinglyimportant. In many instances, however, it may be difficult to ensure thesafety and security of such information while also optimizing theefficient and effective technical operations of the computer systemsthat maintain such information and/or provide such automated andelectronic services.

SUMMARY

Aspects of the disclosure provide effective, efficient, scalable, andconvenient technical solutions that address and overcome the technicalproblems associated with providing information security and optimizingthe efficient and effective technical operations of computer systems. Inparticular, one or more aspects of the disclosure provide techniques forprocessing client device request data using multicomputer processing aswell as a centralized event orchestrator to improve information securityand enhance technical performance.

In accordance with one or more embodiments, a computing platform havingat least one processor, a memory, and a communication interface mayreceive, via the communication interface, from a first client computingdevice, first event definition information defining a first event, andthe first event definition information may include first stimulusselection information associated with the first event. Subsequently, thecomputing platform may receive, via the communication interface, from afirst recipient computing device associated with the first event, afirst request for a recipient-selection user interface. Based onreceiving the first request for the recipient-selection user interfacefrom the first recipient computing device associated with the firstevent, the computing platform may identify one or more stimulus optionsavailable for a first user of the first recipient computing deviceassociated with the first event based on the first stimulus selectioninformation associated with the first event. Based on identifying theone or more stimulus options available for the first user of the firstrecipient computing device associated with the first event, thecomputing platform may send, via the communication interface, to thefirst recipient computing device associated with the first event, afirst delivery selection user interface. In addition, the first deliveryselection user interface may include a first user-selectable componentthat, when invoked, causes the computing platform to create a first newendpoint associated with a first stimulus option of the one or morestimulus options identified as being available for the first user of thefirst recipient computing device associated with the first event.

Thereafter, the computing platform may receive, via the communicationinterface, from the first recipient computing device associated with thefirst event, first delivery selection information. The first deliveryselection information may include information indicating that the firstuser-selectable component has been invoked, and the first deliveryselection information may include information identifying the first newendpoint associated with the first stimulus option as a firstdestination for the first event selected by the first user of the firstrecipient computing device associated with the first event. Based onreceiving the first delivery selection information from the firstrecipient computing device associated with the first event, thecomputing platform may generate, based on the first delivery selectioninformation, one or more first event orchestration commands directing anevent processor to execute one or more actions associated with the firstevent. Subsequently, the computing platform may send, via thecommunication interface, to the event processor, the one or more firstevent orchestration commands directing the event processor to executethe one or more actions associated with the first event.

In some embodiments, receiving the first event definition informationdefining the first event may include receiving information defining oneor more parameters of the first event from the first client computingdevice. In some instances, the information defining the one or moreparameters of the first event may include information defining the firstevent as a single event having a single occurrence. In some instances,the information defining the one or more parameters of the first eventmay include information defining the first event as a recurring eventhaving multiple occurrences.

In some embodiments, the first recipient computing device associatedwith the first event may be linked to a first alias identified as arecipient in the first event definition information. In some instances,the first alias identified as the recipient in the first eventdefinition information may include an email address. In some instances,the first alias identified as the recipient in the first eventdefinition information may include a mobile telephone number.

In some embodiments, identifying the one or more stimulus optionsavailable for the first user of the first recipient computing deviceassociated with the first event comprises identifying at least onestimulus option as available for the first user of the first recipientcomputing device associated with the first event based on the at leastone stimulus option being specified by a user of the first clientcomputing device in the first stimulus selection information associatedwith the first event.

In some embodiments, the event processor may be an internal eventprocessor operated by an entity operating the computing platform. Insome embodiments, the event processor may be an external event processoroperated by a third-party entity not associated with an entity operatingthe computing platform.

In some embodiments, the computing platform may receive, via thecommunication interface, from a second client computing device, secondevent definition information defining a second event, and the secondevent definition information may include second stimulus selectioninformation associated with the second event. Subsequently, thecomputing platform may receive, via the communication interface, from asecond recipient computing device associated with the second event, asecond request for a recipient-selection user interface. Based onreceiving the second request for the recipient-selection user interfacefrom the second recipient computing device associated with the secondevent, the computing platform may identify one or more stimulus optionsavailable for a second user of the second recipient computing deviceassociated with the second event based on the second stimulus selectioninformation associated with the second event. Based on identifying theone or more stimulus options available for the second user of the secondrecipient computing device associated with the second event, thecomputing platform may send, via the communication interface, to thesecond recipient computing device associated with the second event, asecond delivery selection user interface. In addition, the seconddelivery selection user interface may include a second user-selectablecomponent that, when invoked, causes the computing platform to create asecond new endpoint associated with a second stimulus option of the oneor more stimulus options identified as being available for the seconduser of the second recipient computing device associated with the secondevent.

Thereafter, the computing platform may receive, via the communicationinterface, from the second recipient computing device associated withthe second event, second delivery selection information. The seconddelivery selection information may include information indicating thatthe second user-selectable component has been invoked, and the seconddelivery selection information may include information identifying thesecond new endpoint associated with the second stimulus option as asecond destination for the second event selected by the second user ofthe second recipient computing device associated with the second event.Based on receiving the second delivery selection information from thesecond recipient computing device associated with the second event, thecomputing platform may generate, based on the second delivery selectioninformation, one or more second event orchestration commands directingthe event processor to execute one or more actions associated with thesecond event. Subsequently, the computing platform may send, via thecommunication interface, to the event processor, the one or more secondevent orchestration commands directing the event processor to executethe one or more actions associated with the second event.

In some embodiments, receiving the second event definition informationdefining the second event may include receiving information defining oneor more parameters of the second event from the second client computingdevice. In some instances, the information defining the one or moreparameters of the second event may include information defining thesecond event as a single event having a single occurrence. In someinstances, the information defining the one or more parameters of thesecond event may include information defining the second event as arecurring event having multiple occurrences.

In some embodiments, the second recipient computing device associatedwith the second event may be linked to a second alias identified as arecipient in the second event definition information. In some instances,the second alias identified as the recipient in the second eventdefinition information may include an email address. In some instances,the second alias identified as the recipient in the second eventdefinition information may include a mobile telephone number.

In some embodiments, identifying the one or more stimulus optionsavailable for the second user of the second recipient computing deviceassociated with the second event may include identifying at least onestimulus option as available for the second user of the second recipientcomputing device associated with the second event based on the at leastone stimulus option being specified by a user of the second clientcomputing device in the second stimulus selection information associatedwith the second event.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIGS. 1A and 1B depict an illustrative computing environment formulticomputer processing of client device request data using acentralized event orchestrator in accordance with one or more exampleembodiments;

FIGS. 2A-2J depict an illustrative event sequence for multicomputerprocessing of client device request data using a centralized eventorchestrator in accordance with one or more example embodiments;

FIGS. 3-6 depict example graphical user interfaces for multicomputerprocessing of client device request data using a centralized eventorchestrator in accordance with one or more example embodiments; and

FIG. 7 depicts an illustrative method for multicomputer processing ofclient device request data using a centralized event orchestrator inaccordance with one or more example embodiments.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

It is noted that various connections between elements are discussed inthe following description. It is noted that these connections aregeneral and, unless specified otherwise, may be direct or indirect,wired or wireless, and that the specification is not intended to belimiting in this respect. Some aspects of the disclosure relate toincentivizing a recipient of a cross-border and/or cross-currencypayment to select to receive the payment in non-monetary form (e.g., asa prepaid gift card). The payment may be made to the recipient by anorganization, such as a treasury client of a financial institution,which may define the specific incentive(s) to be offered to therecipient. These aspects and other aspects of the disclosure areillustrated in greater detail below.

FIGS. 1A and 1B depict an illustrative computing environment formulticomputer processing of client device request data using acentralized event orchestrator in accordance with one or more exampleembodiments. Referring to FIG. 1A, computing environment 100 may includeone or more computing devices and/or other computer systems. Forexample, computing environment 100 may include an event orchestrationcomputing platform 110, a user interface computing platform 120, anevent recording computing platform 130, an external event processinginterface 140, an internal event processor 145, a first external eventprocessor 150, a second external event processor 155, a first clientcomputing device 160, a second client computing device 165, a firstrecipient computing device 170, and a second recipient computing device175.

Event orchestration computing platform 110 may be configured toorchestrate events that are defined and/or requested by one or moreclient devices, control and/or direct actions of other devices and/orcomputer systems (e.g., in orchestrating events that are defined and/orrequested by one or more client devices and/or in performing otheractions), and/or perform other functions, as discussed in greater detailbelow. In some instances, event orchestration computing platform 110 mayperform and/or provide one or more transaction processing functions,risk analysis functions, and/or other related functions.

User interface computing platform 120 may be configured to generate oneor more user interfaces that are provided to other computer systemsand/or devices in computing environment 100, including client computingdevice 160, client computing device 165, recipient computing device 170,and recipient computing device 175. In some instances, the one or moreuser interfaces that are generated by user interface computing platform120 may be served to such other computer systems and/or devices by eventorchestration computing platform 110, as illustrated in greater detailbelow. Event recording computing platform 130 may be configured tostore, maintain, and/or update one or more records associated with oneor more events occurring in computing environment 100, including one ormore events orchestrated by event orchestration computing platform 110and/or otherwise associated with event orchestration computing platform110.

External event processing interface 140 may be configured to facilitateprocessing of one or more events that are orchestrated by eventorchestration computing platform 110 and/or otherwise associated withevent orchestration computing platform 110 and that may be performed byand/or involve one or more external event processors, such as externalevent processor 150 and external event processor 155. For example, eventorchestration computing platform 110 may be operated by and/or otherwiseassociated with a particular organization (e.g., a financialinstitution) and may, in some instances, be configured to orchestrateand/or control one or more events (e.g., payments transactions,including cross-border payment transactions and/or cross-currencypayment transactions). In addition, external event processor 150 andexternal event processor 155 may, for example, be operated by and/orotherwise associated with one or more other organizations (e.g., paymentprocessors, credit networks, debit networks, digital wallet services,and/or the like) different from the particular organization operatingevent orchestration computing platform 110 (e.g., different from thefinancial institution operating event orchestration computing platform110). In some instances, external event processing interface 140 may beprovided with and/or include one or more dedicated communication linksand/or dedicated communication channels, which may directly and/orsecurely connect external event processing interface 140 to the one ormore external event processors, including external event processor 150and/or external event processor 155.

Internal event processor 145 may be operated by and/or configured toprocess events associated with the same organization that may operateevent orchestration computing platform 110. For example, internal eventprocessor 145 may support operations of and/or be associated with acredit network provided by the organization operating eventorchestration computing platform 110, a debit network provided by theorganization operating event orchestration computing platform 110,and/or a digital wallet service provided by the organization operatingevent orchestration computing platform 110. In addition, paymenttransactions and/or other events orchestrated by event orchestrationcomputing platform 110 that involve transfers of funds between accountsmaintained by the organization operating event orchestration computingplatform 110, other actions performed with respect to accountsmaintained by the organization operating event orchestration computingplatform 110, and/or other intra-organization events orchestrated byevent orchestration computing platform 110, may be processed by internalevent processor 145, as illustrated in greater detail below. In someinstances, when processing cross-border and/or cross-currency paymenttransactions and/or other events orchestrated by event orchestrationcomputing platform 110, internal event processor 145 may perform and/orprovide one or more currency exchange functions, accounting functions,compliance functions, and/or the like.

External event processor 150 may be operated by and/or configured toprocess events associated with a first service provider or entity (e.g.,different from the organization operating event orchestration computingplatform 110), such as a payment processor, a credit network, a debitnetwork, a digital wallet service, and/or the like. External eventprocessor 155 may be operated by and/or configured to process eventsassociated with a second service provider or entity (e.g., differentfrom the organization operating event orchestration computing platform110), such as a payment processor, a credit network, a debit network, adigital wallet service, and/or the like, different from the firstservice provider. For example, external event processor 150 may beassociated with a first payment services provider or digital walletservice operating in a first country and/or maintaining funds in a firstcurrency, and external event processor 155 may be associated with asecond payment services provider or digital wallet service operating ina second country and/or maintaining funds in a second currency. In someinstances, when processing cross-border and/or cross-currency paymenttransactions and/or other events orchestrated by event orchestrationcomputing platform 110, external event processor 150 and/or externalevent processor 155 may perform and/or provide one or more currencyexchange functions, accounting functions, compliance functions, and/orthe like.

Client computing device 160 may be configured to be used by a firstcustomer of an organization, such as an individual client or personalbanking customer of a financial institution, or a commercial client ortreasury client of a financial institution. In some instances, clientcomputing device 160 may, for example, be registered with theorganization and/or one or more computer systems in computingenvironment 100, such that the organization and/or the one or morecomputer systems maintain one or more records linking client computingdevice 160 to the first customer of the organization. Client computingdevice 165 may be configured to be used by a second customer of theorganization (which may, e.g., be different from the first customer ofthe organization). In some instances, client computing device 165 may,for example, be registered with the organization and/or one or morecomputer systems in computing environment 100, such that theorganization and/or the one or more computer systems maintain one ormore records linking client computing device 165 to the second customerof the organization.

Recipient computing device 170 may be configured to be used by a firstrecipient associated with an event, such as a first recipient of fundsassociated with a first payment transaction event. Recipient computingdevice 175 may be configured to be used by a second recipient associatedwith an event, such as a second recipient of funds associated with asecond payment transaction event.

In one or more arrangements, user interface computing platform 120,event recording computing platform 130, external event processinginterface 140, internal event processor 145, external event processor150, external event processor 155, client computing device 160, clientcomputing device 165, recipient computing device 170, and recipientcomputing device 175 may be any type of computing device capable ofreceiving a user interface, receiving input via the user interface, andcommunicating the received input to one or more other computing devices.For example, user interface computing platform 120, event recordingcomputing platform 130, external event processing interface 140,internal event processor 145, external event processor 150, externalevent processor 155, client computing device 160, client computingdevice 165, recipient computing device 170, and recipient computingdevice 175 may, in some instances, be and/or include server computers,desktop computers, laptop computers, tablet computers, smart phones, orthe like that may include one or more processors, memories,communication interfaces, storage devices, and/or other components. Asnoted above, and as illustrated in greater detail below, any and/or allof user interface computing platform 120, event recording computingplatform 130, external event processing interface 140, internal eventprocessor 145, external event processor 150, external event processor155, client computing device 160, client computing device 165, recipientcomputing device 170, and recipient computing device 175 may, in someinstances, be special-purpose computing devices configured to performspecific functions.

Computing environment 100 also may include one or more computingplatforms. For example, and as noted above, computing environment 100may include event orchestration computing platform 110. As illustratedin greater detail below, event orchestration computing platform 110 mayinclude one or more computing devices configured to perform one or moreof the functions described herein. For example, event orchestrationcomputing platform 110 may include one or more computers (e.g., laptopcomputers, desktop computers, servers, server blades, or the like).

Computing environment 100 also may include one or more networks, whichmay interconnect one or more of event orchestration computing platform110, user interface computing platform 120, event recording computingplatform 130, external event processing interface 140, internal eventprocessor 145, external event processor 150, external event processor155, client computing device 160, client computing device 165, recipientcomputing device 170, and recipient computing device 175. For example,computing environment 100 may include private network 190 and publicnetwork 195. Private network 190 and/or public network 195 may includeone or more sub-networks (e.g., local area networks (LANs), wide areanetworks (WANs), or the like). Private network 190 may be associatedwith a particular organization (e.g., a corporation, financialinstitution, educational institution, governmental institution, or thelike) and may interconnect one or more computing devices associated withthe organization. For example, event orchestration computing platform110, user interface computing platform 120, event recording computingplatform 130, external event processing interface 140, and internalevent processor 145 may be associated with an organization (e.g., afinancial institution), and private network 190 may be associated withand/or operated by the organization, and may include one or morenetworks (e.g., LANs, WANs, virtual private networks (VPNs), or thelike) that interconnect event orchestration computing platform 110, userinterface computing platform 120, event recording computing platform130, external event processing interface 140, internal event processor145, and one or more other computing devices and/or computer systemsthat are used by, operated by, and/or otherwise associated with theorganization. Public network 195 may connect private network 190 and/orone or more computing devices connected thereto (e.g., eventorchestration computing platform 110, user interface computing platform120, event recording computing platform 130, external event processinginterface 140, internal event processor 145) with one or more networksand/or computing devices that are not associated with the organization.For example, external event processor 150, external event processor 155,client computing device 160, client computing device 165, recipientcomputing device 170, and recipient computing device 175 might not be,associated with an organization that operates private network 190 (e.g.,because external event processor 150, external event processor 155,client computing device 160, client computing device 165, recipientcomputing device 170, and recipient computing device 175 may be owned,operated, and/or serviced by one or more entities different from theorganization that operates private network 190, such as one or morecustomers of the organization and/or vendors of the organization, ratherthan being owned and/or operated by the organization itself or anemployee or affiliate of the organization), and public network 195 mayinclude one or more networks (e.g., the internet) that connect externalevent processor 150, external event processor 155, client computingdevice 160, client computing device 165, recipient computing device 170,and recipient computing device 175 to private network 190 and/or one ormore computing devices connected thereto (e.g., event orchestrationcomputing platform 110, user interface computing platform 120, eventrecording computing platform 130, external event processing interface140, internal event processor 145).

Referring to FIG. 1B, event orchestration computing platform 110 mayinclude one or more processors 111, memory 112, and communicationinterface 115. A data bus may interconnect processor(s) 111, memory 112,and communication interface 115. Communication interface 115 may be anetwork interface configured to support communication between eventorchestration computing platform 110 and one or more networks (e.g.,private network 190, public network 195, or the like). Memory 112 mayinclude one or more program modules having instructions that whenexecuted by processor(s) 111 cause event orchestration computingplatform 110 to perform one or more functions described herein and/orone or more databases that may store and/or otherwise maintaininformation which may be used by such program modules and/orprocessor(s) 111. In some instances, the one or more program modulesand/or databases may be stored by and/or maintained in different memoryunits of event orchestration computing platform 110 and/or by differentcomputing devices that may form and/or otherwise make up eventorchestration computing platform 110. For example, memory 112 may have,store, and/or include an event orchestration module 113, an eventorchestration database 114, and a dynamic stimulus engine 116. Eventorchestration module 113 may have instructions that direct and/or causeevent orchestration computing platform 110 to orchestrate one or moreevents involving one or more other computing devices and/or computersystems in computing environment 100 and/or perform other functions, asdiscussed in greater detail below. Event orchestration database 114 maystore information used by event orchestration module 113 and/or eventorchestration computing platform 110 in orchestrating one or more eventsinvolving one or more other computing devices and/or computer systems incomputing environment 100 and/or in performing other functions. Dynamicstimulus engine 116 may have instructions that direct and/or cause eventorchestration computing platform 110 to evaluate and/or determine, inreal-time and/or on a continuous basis, whether a dynamic stimulusoption is available during orchestration of a particular event, presentone or more graphical user interfaces and/or interface elementsassociated with a dynamic stimulus option, dynamically create one ormore new endpoints based on activation and/or invocation of a dynamicstimulus option during orchestration of a particular event, and/orperform other functions.

FIGS. 2A-2J depict an illustrative event sequence for multicomputerprocessing of client device request data using a centralized eventorchestrator in accordance with one or more example embodiments.Referring to FIG. 2A, at step 201, event orchestration computingplatform 110 may receive a request to define a new event from clientcomputing device 160. For example, at step 201, event orchestrationcomputing platform 110 may receive a message from client computingdevice 160 requesting an event definition user interface and/or otheruser interface via which a new event and/or one or more associated eventparameters may be defined.

In some instances, the request to define a new event received fromclient computing device 160 at step 201 may be and/or include a requestto define a new payment transaction event, such as a cross-border and/orcross-currency payment transaction event, to be orchestrated by eventorchestration computing platform 110. For instance, event orchestrationcomputing platform 110 may be operated by and/or associated with afinancial institution, and client computing device 160 may be operatedby and/or associated with an individual client of the financialinstitution or a treasury client of the financial institution. Theclient of the financial institution associated with client computingdevice 160 may, for instance, request to define a new paymenttransaction event, such as a cross-border and/or cross-currency paymenttransaction event, that is to be orchestrated by event orchestrationcomputing platform 110 and that may involve a payment by the client ofthe financial institution to a specific recipient (which may, e.g., beassociated with a specific recipient device, such as recipient computingdevice 170). As illustrated in greater detail below, the client of thefinancial institution may identify the specific recipient of the newpayment transaction event only by an alias, such as an email address, amobile telephone number, a social networking handle, and/or the like(e.g., rather than identifying the specific recipient of the new paymenttransaction event by a legal name and/or account number), and eventorchestration computing platform 110 may use this alias information tocontact the specific recipient of the new payment transaction event andprovide them with recipient-selection functionality that allows thespecific recipient of the new payment transaction event to select howthey would like to receive the funds corresponding to the new paymenttransaction event (e.g., in a particular digital wallet, bank account,and/or the like). In addition, the new payment transaction event may, insome instances, be a cross-border payment transaction event in which theclient of the financial institution and the specific recipient of thenew payment transaction may be located in and/or otherwise be associatedwith different countries. Additionally or alternatively, the new paymenttransaction event may, in some instances, be a cross-currency paymenttransaction event in which the client of the financial institution mayprovide funds to the financial institution for payment in a firstcurrency, and in which the specific recipient of the new paymenttransaction may receive the funds in a second currency different fromthe first currency.

At step 202, event orchestration computing platform 110 may send one ormore commands to user interface computing platform 120 directing userinterface computing platform 120 to generate a user interface. Forexample, at step 202, event orchestration computing platform 110 maygenerate and/or send one or more commands to user interface computingplatform 120 directing user interface computing platform 120 to generatea user interface that is configured to allow a user of client computingdevice 160 to define a new event, such as a new cross-border and/orcross-currency payment transaction event, to be orchestrated by eventorchestration computing platform 110. The one or more commands generatedby event orchestration computing platform 110 and/or sent by eventorchestration computing platform 110 to user interface computingplatform 120 may include parameters and/or other information identifyinga client of an organization operating event orchestration computingplatform 110 with which the request to define the new event isassociated (e.g., the client of the organization linked to and/orotherwise associated with client computing device 160), parametersand/or other information identifying the user interface that isrequested, and/or other parameters and information. At step 203, eventorchestration computing platform 110 may receive a user interfacegenerated by user interface computing platform 120 from user interfacecomputing platform 120. For example, at step 203, event orchestrationcomputing platform 110 may receive from user interface computingplatform 120 a user interface generated by user interface computingplatform 120 based on the one or more commands sent to user interfacecomputing platform 120 by event orchestration computing platform 110.

At step 204, event orchestration computing platform 110 may send theuser interface to client computing device 160. In sending the userinterface to client computing device 160, event orchestration computingplatform 110 may cause client computing device 160 to display and/orotherwise present the user interface generated by user interfacecomputing platform 120 based on the one or more commands sent to userinterface computing platform 120 by event orchestration computingplatform 110. For example, in sending the user interface to clientcomputing device 160, event orchestration computing platform 110 maycause client computing device 160 to display and/or otherwise present agraphical user interface similar to graphical user interface 300, whichis illustrated in FIG. 3. As seen in FIG. 3, graphical user interface300 may include one or more fields, controls, and/or other elements thatmay allow a user of client computing device 160 to define a new event,such as a new cross-border and/or cross-currency payment transactionevent, to be orchestrated by event orchestration computing platform 110.For example, graphical user interface 300 may include one or morefields, controls, and/or other elements that may allow a user of clientcomputing device 160 to specify and/or otherwise define an event dateparameter associated with the new event, an event type parameterassociated with the new event, an event occurrence parameter associatedwith the new event, an event recipient parameter associated with the newevent, an event stimulus parameter associated with the new event, and/orother parameters associated with the new event.

In addition, and as seen in FIG. 3, graphical user interface 300 mayinclude one or more fields, controls, and/or other elements that mayallow a user of client computing device 160 to identify a recipientassociated with the event using an alias, such as an email address, amobile telephone number, a social networking handle, and/or the like(e.g., rather than identifying the recipient of the new event by a legalname and/or account number), and event orchestration computing platform110 subsequently may use this alias information to contact the specificrecipient of the new event and provide them with recipient-selectionfunctionality (which may, e.g., allow the specific recipient of a newpayment transaction event to select how they would like to receive thefunds corresponding to the new payment transaction event, such as in aparticular digital wallet, bank account, and/or the like). Graphicaluser interface 300 also may include one or more fields, controls, and/orother elements that may allow a user of client computing device 160 toview and/or select various stimulus options that may be available inconnection with a new event (e.g., “View/Select Other StimulusOptions”). Such other stimulus options that may be available inconnection with the new event may, for example, include one or morestimulus options that are designed to incentivize a recipient of the newevent to select to receive funds associated with the new event via aparticular delivery method, such as in a new account maintained by afinancial institution operating event orchestration computing platform110 or a different financial institution, via a prepaid debit cardusable via one or more debit networks, via a gift card that isredeemable with and/or otherwise usable with a merchant client or othertreasury client defining the new event, and/or the like.

Referring to FIG. 2B, at step 205, event orchestration computingplatform 110 may receive event definition information from clientcomputing device 160, and the event definition information received byevent orchestration computing platform 110 from client computing device160 may, in some instances, include stimulus selection informationspecified by a user of client computing device 160. For example, at step205, event orchestration computing platform 110 may receive, via thecommunication interface (e.g., communication interface 115), from afirst client computing device (e.g., client computing device 160), firstevent definition information defining a first event, and the first eventdefinition information may include first stimulus selection informationassociated with the first event. The first event definition informationdefining the first event to be orchestrated by event orchestrationcomputing platform 110 and the first stimulus selection informationassociated with the first event may, for instance, be received via anevent definition user interface generated by user interface computingplatform 120 and sent to client computing device 160 by eventorchestration computing platform 110 (e.g., the user interface sent byevent orchestration computing platform 110 to client computing device160 at step 204). In addition, the first stimulus selection informationassociated with the first event may, for example, identify one or morespecific stimulus options specified by the user of client computingdevice 160 to be offered to the recipient of the new event as incentivesto receive funds associated with the new event via a particular deliverymethod corresponding to the one or more specific stimulus optionsspecified by the user of client computing device 160. For example, thefirst stimulus selection information associated with the first eventmay, for example, identify and/or specify that the recipient of the newevent should be prompted to select whether to receive funds associatedwith the new event in a new account maintained by a financialinstitution operating event orchestration computing platform 110 or adifferent financial institution, via a prepaid debit card usable via oneor more debit networks, via a gift card that is redeemable with and/orotherwise usable with a merchant client or other treasury client usingclient computing device 160 to define the new event, and/or via one ormore other delivery methods associated with other stimulus options.

In some embodiments, receiving the first event definition informationdefining the first event may include receiving information defining oneor more parameters of the first event from the first client computingdevice. For example, in receiving the first event definition informationdefining the first event, event orchestration computing platform 110 mayreceive information defining one or more parameters of the first eventfrom the first client computing device (e.g., client computing device160). For example, the first event definition information defining thefirst event to be orchestrated by event orchestration computing platform110 (which may, e.g., be received by event orchestration computingplatform 110 from client computing device 160 at step 205) may includeone or more parameters and/or other information specified by a user ofclient computing device 160. For example, the first event to beorchestrated by event orchestration computing platform 110 may be apayment transaction, and the one or more parameters and/or otherinformation specified by the user of client computing device 160 mayidentify a recipient of the transaction to be paid, an amount to be paidto the recipient of the transaction, whether the transaction has asingle occurrence or multiple occurrences, and/or other characteristicsof the transaction.

In some embodiments, the information defining the one or more parametersof the first event may include information defining the first event as asingle event having a single occurrence. For example, the informationdefining the one or more parameters of the first event (which may, e.g.,be received by event orchestration computing platform 110 from clientcomputing device 160) may include information defining the first eventas a single event having a single occurrence. For instance, the firstevent may correspond to a new payment transaction involving a singlepayment to an identified recipient. In some embodiments, the informationdefining the one or more parameters of the first event may includeinformation defining the first event as a recurring event havingmultiple occurrences. For example, the information defining the one ormore parameters of the first event (which may, e.g., be received byevent orchestration computing platform 110 from client computing device160) may include information defining the first event as a recurringevent having multiple occurrences. For instance, the first event maycorrespond to a new payment transaction involving multiple recurringpayments to an identified recipient.

At step 206, event orchestration computing platform 110 may generate anevent notification. For example, at step 206, event orchestrationcomputing platform 110 may generate an event notification for recipientcomputing device 170 based on receiving event definition informationfrom client computing device 160 identifying an alias linked torecipient computing device 170 as a recipient associated with the eventdefined by the event definition information received from clientcomputing device 160. At step 207, event orchestration computingplatform 110 may send the event notification to recipient computingdevice 170. In sending the event notification to recipient computingdevice 170, event orchestration computing platform 110 may, forinstance, send the event notification to recipient computing device 170via a push notification service associated with an operating systemexecuting on recipient computing device 170. Additionally oralternatively, in sending the event notification to recipient computingdevice 170, event orchestration computing platform 110 may send anelectronic mail message, a short message service message, and/or anothertype of electronic message to recipient computing device 170.

At step 208, event orchestration computing platform 110 may receive arequest for a delivery selection user interface (which may, e.g., alsobe referred to as a recipient-selection user interface) from recipientcomputing device 170. For example, at step 208, event orchestrationcomputing platform 110 may receive, via the communication interface(e.g., communication interface 115), from a first recipient computingdevice associated with the first event (e.g., recipient computing device170), a first request for a recipient-selection user interface. Forinstance, event orchestration computing platform 110 may receive such arequest after recipient computing device 170 sends the request inresponse to receiving a selection or other user input in response topresenting the event notification received from event orchestrationcomputing platform 110.

In some embodiments, the first recipient computing device associatedwith the first event may be linked to a first alias identified as arecipient in the first event definition information. For example, thefirst recipient computing device associated with the first event (e.g.,recipient computing device 170) may be linked to a first aliasidentified as a recipient in the first event definition information(which may, e.g., be received by event orchestration computing platform110 from client computing device 160). In some instances, the firstalias identified as the recipient in the first event definitioninformation (which may, e.g., be received by event orchestrationcomputing platform 110 from client computing device 160) may include anemail address. For example, the first alias identified as the recipientin the first event definition information received by eventorchestration computing platform 110 from client computing device 160may include an email address that is linked to, registered with, and/orotherwise associated with the first recipient computing deviceassociated with the first event (e.g., recipient computing device 170)as an alias of the first recipient computing device associated with thefirst event (e.g., recipient computing device 170). Additionally oralternatively, the first alias identified as the recipient in the firstevent definition information (which may, e.g., be received by eventorchestration computing platform 110 from client computing device 160)may include a mobile telephone number. For example, the first aliasidentified as the recipient in the first event definition informationreceived by event orchestration computing platform 110 from clientcomputing device 160 may include a mobile telephone number that islinked to, registered with, and/or otherwise associated with the firstrecipient computing device associated with the first event (e.g.,recipient computing device 170) as an alias of the first recipientcomputing device associated with the first event (e.g., recipientcomputing device 170).

Referring to FIG. 2C, at step 209, event orchestration computingplatform 110 may identify one or more stimulus options available for auser of recipient computing device 170. For example, at step 209, basedon receiving the first request for the recipient-selection userinterface from the first recipient computing device associated with thefirst event (e.g., recipient computing device 170), event orchestrationcomputing platform 110 may identify one or more stimulus optionsavailable for a first user of the first recipient computing deviceassociated with the first event (e.g., recipient computing device 170)based on the first stimulus selection information associated with thefirst event. In identifying the one or more stimulus options availablefor the first user of the first recipient computing device associatedwith the first event (e.g., recipient computing device 170), eventorchestration computing platform 110 may, for example, select one ormore stimulus options to be offered to the first user of the firstrecipient computing device associated with the first event (e.g.,recipient computing device 170) based on the stimulus selectioninformation associated with the first event received from clientcomputing device 160, based on user profile information corresponding tothe recipient and/or another user of recipient computing device 170,and/or other factors. For example, certain stimulus options may beavailable to a particular user or a particular group of users, andother, different stimulus options may be available to a different useror a different group of users.

In some embodiments, identifying the one or more stimulus optionsavailable for the first user of the first recipient computing deviceassociated with the first event may include identifying at least onestimulus option as available for the first user of the first recipientcomputing device associated with the first event based on the at leastone stimulus option being specified by a user of the first clientcomputing device in the first stimulus selection information associatedwith the first event. For example, in identifying the one or morestimulus options available for the first user of the first recipientcomputing device associated with the first event (e.g., recipientcomputing device 170), event orchestration computing platform 110 mayidentify at least one stimulus option as available for the first user ofthe first recipient computing device associated with the first event(e.g., recipient computing device 170) based on the at least onestimulus option being specified by a user of the first client computingdevice (e.g., client computing device 160) in the first stimulusselection information associated with the first event. For instance,event orchestration computing platform 110 may identify and/or otherwiseselect one or more particular stimulus options to be offered that werespecified by the user of client computing device 160 in the eventdefinition information for the particular event received by eventorchestration computing platform 110 from client computing device 160.

At step 210, event orchestration computing platform 110 may generate oneor more commands directing user interface computing platform 120 togenerate a delivery selection user interface. For example, at step 210,event orchestration computing platform 110 may generate one or morecommands directing user interface computing platform 120 to generate adelivery selection user interface for recipient computing device 170that includes a dynamic stimulus option (e.g., based on identifying theone or more stimulus options available for the user of recipientcomputing device 170). For instance, the one or more commands generatedby event orchestration computing platform 110 may direct user interfacecomputing platform 120 to insert and/or include one or more controlsand/or other user interface elements in the delivery selection userinterface that are configured to offer and/or otherwise provide the oneor more stimulus options that were identified and/or otherwise selectedby event orchestration computing platform 110 for the user of recipientcomputing device 170. At step 211, event orchestration computingplatform 110 may send the one or more commands to user interfacecomputing platform 120 directing user interface computing platform 120to generate a delivery selection user interface. For example, at step211, event orchestration computing platform 110 may send, via thecommunication interface (e.g., communication interface 115), to a userinterface computing platform (e.g., user interface computing platform120), one or more commands directing the user interface computingplatform (e.g., user interface computing platform 120) to generate thedelivery selection user interface. The one or more commands generated byevent orchestration computing platform 110 and/or sent by eventorchestration computing platform 110 to user interface computingplatform 120 may include parameters and/or other information identifyingthe first recipient computing device associated with the first event(e.g., recipient computing device 170) and/or the entity identified asthe recipient for the first event (e.g., a registered and/or authorizeduser of recipient computing device 170), parameters and/or otherinformation identifying the user interface that is requested (e.g., oneor more parameters directing and/or causing user interface computingplatform 120 to include the identified stimulus options in the deliveryselection user interface), and/or other parameters and information.

At step 212, event orchestration computing platform 110 may receive adelivery selection user interface generated by user interface computingplatform 120 from user interface computing platform 120. For example, atstep 212, event orchestration computing platform 110 may receive, viathe communication interface (e.g., communication interface 115), fromthe user interface computing platform (e.g., user interface computingplatform 120), the delivery selection user interface. For instance, atstep 212, event orchestration computing platform 110 may receive fromuser interface computing platform 120 a user interface generated by userinterface computing platform 120 based on the one or more commands sentto user interface computing platform 120 by event orchestrationcomputing platform 110.

Referring to FIG. 2D, at step 213, event orchestration computingplatform 110 may send the delivery selection user interface generated byuser interface computing platform 120 to recipient computing device 170.For example, at step 213, based on identifying the one or more stimulusoptions available for the first user of the first recipient computingdevice associated with the first event (e.g., recipient computing device170), event orchestration computing platform 110 may send, via thecommunication interface (e.g., communication interface 115), to thefirst recipient computing device associated with the first event (e.g.,recipient computing device 170), a first delivery selection userinterface. In addition, the first delivery selection user interface mayinclude a first user-selectable component that, when invoked, causes thecomputing platform (e.g., event orchestration computing platform 110) tocreate a first new endpoint associated with a first stimulus option ofthe one or more stimulus options identified as being available for thefirst user of the first recipient computing device associated with thefirst event (e.g., recipient computing device 170). For instance, thedelivery selection user interface generated by user interface computingplatform 120 and sent to recipient computing device 170 by eventorchestration computing platform 110 may include a user-selectablecomponent (e.g., a button, a hyperlink, a pull-down menu, and/or thelike) that, when invoked, causes event orchestration computing platform110 to create a new endpoint associated with a specific user-selectedstimulus option of the one or more stimulus options identified as beingavailable for the user of recipient computing device 170.

In sending the first delivery selection user interface to the firstrecipient computing device associated with the first event (e.g.,recipient computing device 170), event orchestration computing platform110 may cause recipient computing device 170 to display and/or otherwisepresent the user interface generated by user interface computingplatform 120 based on the one or more commands sent to user interfacecomputing platform 120 by event orchestration computing platform 110.For example, in sending the first delivery selection user interface tothe first recipient computing device associated with the first event(e.g., recipient computing device 170), event orchestration computingplatform 110 may cause recipient computing device 170 to display and/orotherwise present a graphical user interface similar to graphical userinterface 400, which is illustrated in FIG. 4. As seen in FIG. 4,graphical user interface 400 may include one or more fields, controls,and/or other elements that may allow a user of recipient computingdevice 170 to select and/or specify a delivery destination for the firstevent, such as a delivery destination for funds associated with across-border and/or cross-currency payment transaction event beingorchestrated by event orchestration computing platform 110. For example,graphical user interface 400 may include one or more fields, controls,and/or other elements that may allow a user of recipient computingdevice 170 to specify and/or otherwise define a destination parameterassociated with the event, a destination type parameter associated withthe event (which may, e.g., indicate a destination country and/or adestination currency for a cross-border and/or cross-currency paymenttransaction event), and/or other parameters associated with the newevent. In addition, graphical user interface 400 may include auser-selectable option (e.g., “Stimulus-Destination-1|Other Options”)that, when invoked by the user of recipient computing device 170, causesevent orchestration computing platform 110 to create a new endpointassociated with a specific user-selected stimulus option of the one ormore stimulus options identified as being available for the user ofrecipient computing device 170. For example, graphical user interface400 may be configured to present the one or more stimulus optionsidentified as being available for the user of recipient computing device170 (e.g., in response to receiving input selecting “Other Options”)and/or may be configured to cause event orchestration computing platform110 to create a new endpoint associated with a particular optionselected by the user of recipient computing device 170 via graphicaluser interface 400 (e.g., “Stimulus-Destination-1”).

At step 214, event orchestration computing platform 110 may receivedelivery selection information from recipient computing device 170. Forexample, at step 214, event orchestration computing platform 110 mayreceive, via the communication interface (e.g., communication interface115), from the first recipient computing device associated with thefirst event (e.g., recipient computing device 170), first deliveryselection information. In addition, the first delivery selectioninformation (which may, e.g., be received by event orchestrationcomputing platform 110 from recipient computing device 170) may includeinformation indicating that the first user-selectable component has beeninvoked. Further, the first delivery selection information (which may,e.g., be received by event orchestration computing platform 110 fromrecipient computing device 170) may include information identifying thefirst new endpoint associated with the first stimulus option as a firstdestination for the first event selected by the first user of the firstrecipient computing device associated with the first event (e.g.,recipient computing device 170). For instance, event orchestrationcomputing platform 110 may receive from recipient computing device 170delivery selection information that includes information indicating thatthe user-selectable component has been invoked (which may, e.g., causeevent orchestration computing platform 110 to create a new endpointassociated with a specific user-selected stimulus option) and thatfurther includes information identifying the new endpoint (which may,e.g., be subsequently created by event orchestration computing platform110, as illustrated below) as the destination that has been selected bythe user of recipient computing device 170 to be the destination for theparticular event.

At step 215, event orchestration computing platform 110 may validate thedelivery selection information received from recipient computing device170. For example, at step 215, event orchestration computing platform110 may validate the delivery selection information received from therecipient computing device (e.g., recipient computing device 170). Invalidating the delivery selection information received from therecipient computing device (e.g., recipient computing device 170), eventorchestration computing platform 110 may, for example, execute and/orapply one or more risk analysis evaluation algorithms, regulatorycompliance evaluation algorithms, account verification evaluationalgorithms, identity verification evaluation algorithms, and/or otheralgorithms to determine whether the delivery selection informationreceived from the recipient computing device (e.g., recipient computingdevice 170) is valid. If event orchestration computing platform 110determines that the delivery selection information received from therecipient computing device (e.g., recipient computing device 170) isinvalid, event orchestration computing platform 110 may generate and/orsend one or more error messages (e.g., to event recording computingplatform 130, client computing device 160, recipient computing device170, and/or one or more other systems and/or devices). Alternatively, ifevent orchestration computing platform 110 determines that the deliveryselection information received from the recipient computing device(e.g., recipient computing device 170) is valid, the event sequence maycontinue to step 216 as illustrated in FIG. 2D.

At step 216, event orchestration computing platform 110 may create a newendpoint based on the delivery selection information received fromrecipient computing device 170. For example, at step 216, eventorchestration computing platform 110 may create a first new endpointassociated with a first stimulus option of the one or more stimulusoptions identified as being available for the first user of the firstrecipient computing device associated with the first event (e.g.,recipient computing device 170) in response to receiving the informationindicating that the first user-selectable component has been invoked.For instance, event orchestration computing platform 110 may create anew endpoint corresponding to the stimulus option that has been selectedby the user of recipient computing device 170, and the new endpoint maybe a new account maintained by a financial institution operating eventorchestration computing platform 110 or a different financialinstitution, a prepaid debit card usable via one or more debit networks,a gift card that is redeemable with and/or otherwise usable with amerchant client or other treasury client which defined the first event,and/or the like.

In some embodiments, creating the first new endpoint associated with thefirst stimulus option of the one or more stimulus options may include:generating one or more commands directing an event recording computingplatform to create at least one record corresponding to the first newendpoint for the first user of the first recipient computing deviceassociated with the first event; and sending, via the communicationinterface, to the event recording computing platform, the one or morecommands directing the event recording computing platform to create theat least one record corresponding to the first new endpoint for thefirst user of the first recipient computing device associated with thefirst event. For example, in creating the first new endpoint associatedwith the first stimulus option of the one or more stimulus options forthe first user of the first recipient computing device associated withthe first event (e.g., recipient computing device 170), eventorchestration computing platform 110 may generate one or more commandsdirecting an event recording computing platform (e.g., event recordingcomputing platform 130) to create at least one record corresponding tothe first new endpoint for the first user of the first recipientcomputing device associated with the first event (e.g., recipientcomputing device 170). In addition, event orchestration computingplatform 110 may send, via the communication interface (e.g.,communication interface 115), to the event recording computing platform(e.g., event recording computing platform 130), the one or more commandsdirecting the event recording computing platform (e.g., event recordingcomputing platform 130) to create the at least one record correspondingto the first new endpoint for the first user of the first recipientcomputing device associated with the first event (e.g., recipientcomputing device 170). For example, the new endpoint may be a newaccount maintained by a financial institution operating eventorchestration computing platform 110, such as a new foreign,cross-currency banking account or digital wallet account, and the atleast one record may include a unique identifier, initial balance,and/or other information associated with the new account being createdby event orchestration computing platform 110 in response to theinvocation of the dynamic stimulus option. In other examples, the newendpoint may be a new account maintained by a different financialinstitution than the financial institution operating event orchestrationcomputing platform 110, a prepaid debit card usable via one or moredebit networks, a gift card that is redeemable with and/or otherwiseusable with a merchant client or other treasury client which defined thefirst event, and/or the like. In these other instances, event recordingcomputing platform 130 also may create and/or maintain one or morerecords associated with the new endpoint (e.g., based on commandsgenerated and/or sent to event recording computing platform 130 by eventorchestration computing platform 110).

Referring to FIG. 2E, at step 217, event orchestration computingplatform 110 may generate one or more event orchestration commands. Forexample, at step 217, based on receiving the first delivery selectioninformation from the first recipient computing device associated withthe first event (e.g., recipient computing device 170), eventorchestration computing platform 110 may generate, based on the firstdelivery selection information, one or more first event orchestrationcommands directing an event processor (e.g., internal event processor145) to execute one or more actions associated with the first event. Forinstance, event orchestration computing platform 110 may generate one ormore commands directing and/or controlling internal event processor 145to execute one or more actions associated with the first event, such asone or more actions that perform and/or complete a payment transactioncorresponding to the first event. For example, the one or more commandsgenerated by event orchestration computing platform 110 may directinternal event processor 145 (which may, e.g., be associated with aparticular digital wallet service, banking service, or the like) totransfer funds to the new endpoint (which may, e.g., be a new account, anew prepaid debit card, a new gift card, and/or the like, correspondingto the selected stimulus option) created by event orchestrationcomputing platform 110 and selected by the user of the first recipientcomputing device associated with the first event (e.g., recipientcomputing device 170).

At step 218, event orchestration computing platform 110 may send the oneor more event orchestration commands to internal event processor 145.For example, at step 218, event orchestration computing platform 110 maysend, via the communication interface (e.g., communication interface115), to the event processor (e.g., internal event processor 145), theone or more first event orchestration commands directing the eventprocessor (e.g., internal event processor 145) to execute the one ormore actions associated with the first event. In some instances, theevent processor (to which event orchestration computing platform 110may, e.g., send the one or more event orchestration commands) may be aninternal event processor (e.g., internal event processor 145) operatedby an entity operating the computing platform (e.g., event orchestrationcomputing platform 110). In other instances, the event processor (towhich event orchestration computing platform 110 may, e.g., send the oneor more event orchestration commands) may be an external event processor(e.g., external event processor 150, external event processor 155)operated by a third-party entity not associated with an entity operatingthe computing platform (e.g., event orchestration computing platform110). For example, event orchestration computing platform 110 may sendthe one or more event orchestration commands to such an external eventprocessor (e.g., external event processor 150, external event processor155) in instances in which the destination of the event (e.g., the newendpoint) is a new account with a financial institution different fromthe financial institution operating event orchestration computingplatform 110, a prepaid debit card associated with a debit networkprovided by a financial institution different from the financialinstitution operating event orchestration computing platform 110, amerchant gift card that is managed and/or processed by a financialinstitution different from the financial institution operating eventorchestration computing platform 110, and/or the like.

At step 219, event orchestration computing platform 110 may receiveconfirmation information from internal event processor 145. For example,at step 219, event orchestration computing platform 110 may receive frominternal event processor 145 confirmation information indicating thatone or more actions associated with the first event were performedand/or completed by one or more event servers (e.g., internal eventprocessor 145 and/or related servers and/or systems). At step 220, eventorchestration computing platform 110 may send one or more updatecommands to event recording computing platform 130. For example, at step220, event orchestration computing platform 110 may send one or moreupdate commands to event recording computing platform 130 directingevent recording computing platform 130 to update one or more recordsindicating that the first event has been completed and/or that one ormore actions associated with the first event have been performed basedon the one or more event orchestration commands sent to internal eventprocessor 145 by event orchestration computing platform 110 and/or basedon the confirmation information received by event orchestrationcomputing platform 110 from internal event processor 145.

By processing client device request data using multicomputer processingand a centralized event orchestrator (e.g., by implementing thetechniques and/or performing the steps described above), eventorchestration computing platform 110 may provide improved informationsecurity and enhanced technical performance (e.g., when processing oneor more events defined by a client computing device, such as clientcomputing device 160, and involving a particular recipient computingdevice, such as recipient computing device 170). Subsequently, eventorchestration computing platform 110 may execute one or more actions,similar to those discussed above, in processing one or more additionalevents, such as a second event involving client computing device 165 andrecipient computing device 175, as illustrated in the example eventsequence.

Referring to FIG. 2F, at step 221, event orchestration computingplatform 110 may receive a request to define a new event from clientcomputing device 165. For example, at step 221, event orchestrationcomputing platform 110 may receive a message from client computingdevice 165 requesting an event definition user interface and/or otheruser interface via which a new event and/or one or more associated eventparameters may be defined.

In some instances, the request to define a new event received fromclient computing device 165 at step 221 may be and/or include a requestto define a new payment transaction event, such as a cross-border and/orcross-currency payment transaction event, to be orchestrated by eventorchestration computing platform 110. For instance, event orchestrationcomputing platform 110 may be operated by and/or associated with afinancial institution, and client computing device 165 may be operatedby and/or associated with an individual client of the financialinstitution or a treasury client of the financial institution. Theclient of the financial institution associated with client computingdevice 165 may, for instance, request to define a new paymenttransaction event, such as a cross-border and/or cross-currency paymenttransaction event, that is to be orchestrated by event orchestrationcomputing platform 110 and that may involve a payment by the client ofthe financial institution to a specific recipient (which may, e.g., beassociated with a specific recipient device, such as recipient computingdevice 175). As illustrated in greater detail below, the client of thefinancial institution may identify the specific recipient of the newpayment transaction event only by an alias, such as an email address, amobile telephone number, a social networking handle, and/or the like(e.g., rather than identifying the specific recipient of the new paymenttransaction event by a legal name and/or account number), and eventorchestration computing platform 110 may use this alias information tocontact the specific recipient of the new payment transaction event andprovide them with recipient-selection functionality that allows thespecific recipient of the new payment transaction event to select howthey would like to receive the funds corresponding to the new paymenttransaction event (e.g., in a particular digital wallet, bank account,and/or the like). In addition, the new payment transaction event may, insome instances, be a cross-border payment transaction event in which theclient of the financial institution and the specific recipient of thenew payment transaction may be located in and/or otherwise be associatedwith different countries. Additionally or alternatively, the new paymenttransaction event may, in some instances, be a cross-currency paymenttransaction event in which the client of the financial institution mayprovide funds to the financial institution for payment in a secondcurrency, and in which the specific recipient of the new paymenttransaction may receive the funds in a second currency different fromthe second currency.

At step 222, event orchestration computing platform 110 may send one ormore commands to user interface computing platform 120 directing userinterface computing platform 120 to generate a user interface. Forexample, at step 202, event orchestration computing platform 110 maygenerate and/or send one or more commands to user interface computingplatform 120 directing user interface computing platform 120 to generatea user interface that is configured to allow a user of client computingdevice 165 to define a new event, such as a new cross-border and/orcross-currency payment transaction event, to be orchestrated by eventorchestration computing platform 110. The one or more commands generatedby event orchestration computing platform 110 and/or sent by eventorchestration computing platform 110 to user interface computingplatform 120 may include parameters and/or other information identifyinga client of an organization operating event orchestration computingplatform 110 with which the request to define the new event isassociated (e.g., the client of the organization linked to and/orotherwise associated with client computing device 165), parametersand/or other information identifying the user interface that isrequested, and/or other parameters and information. At step 223, eventorchestration computing platform 110 may receive a user interfacegenerated by user interface computing platform 120 from user interfacecomputing platform 120. For example, at step 223, event orchestrationcomputing platform 110 may receive from user interface computingplatform 120 a user interface generated by user interface computingplatform 120 based on the one or more commands sent to user interfacecomputing platform 120 by event orchestration computing platform 110.

At step 224, event orchestration computing platform 110 may send theuser interface to client computing device 165. In sending the userinterface to client computing device 165, event orchestration computingplatform 110 may cause client computing device 165 to display and/orotherwise present the user interface generated by user interfacecomputing platform 120 based on the one or more commands sent to userinterface computing platform 120 by event orchestration computingplatform 110. For example, in sending the user interface to clientcomputing device 165, event orchestration computing platform 110 maycause client computing device 165 to display and/or otherwise present agraphical user interface similar to graphical user interface 500, whichis illustrated in FIG. 5. As seen in FIG. 5, graphical user interface500 may include one or more fields, controls, and/or other elements thatmay allow a user of client computing device 165 to define a new event,such as a new cross-border and/or cross-currency payment transactionevent, to be orchestrated by event orchestration computing platform 110.For example, graphical user interface 500 may include one or morefields, controls, and/or other elements that may allow a user of clientcomputing device 165 to specify and/or otherwise define an event dateparameter associated with the new event, an event type parameterassociated with the new event, an event occurrence parameter associatedwith the new event, an event recipient parameter associated with the newevent, an event stimulus parameter associated with the new event, and/orother parameters associated with the new event.

In addition, and as seen in FIG. 5, graphical user interface 500 mayinclude one or more fields, controls, and/or other elements that mayallow a user of client computing device 165 to identify a recipientassociated with the event using an alias, such as an email address, amobile telephone number, a social networking handle, and/or the like(e.g., rather than identifying the recipient of the new event by a legalname and/or account number), and event orchestration computing platform110 subsequently may use this alias information to contact the specificrecipient of the new event and provide them with recipient-selectionfunctionality (which may, e.g., allow the specific recipient of a newpayment transaction event to select how they would like to receive thefunds corresponding to the new payment transaction event, such as in aparticular digital wallet, bank account, and/or the like). Graphicaluser interface 500 also may include one or more fields, controls, and/orother elements that may allow a user of client computing device 165 toview and/or select various stimulus options that may be available inconnection with a new event (e.g., “View/Select Other StimulusOptions”). Such other stimulus options that may be available inconnection with the new event may, for example, include one or morestimulus options that are designed to incentivize a recipient of the newevent to select to receive funds associated with the new event via aparticular delivery method, such as in a new account maintained by afinancial institution operating event orchestration computing platform110 or a different financial institution, via a prepaid debit cardusable via one or more debit networks, via a gift card that isredeemable with and/or otherwise usable with a merchant client or othertreasury client defining the new event, and/or the like.

Referring to FIG. 2G, at step 225, event orchestration computingplatform 110 may receive event definition information from clientcomputing device 165, and the event definition information received byevent orchestration computing platform 110 from client computing device165 may, in some instances, include stimulus selection informationspecified by a user of client computing device 165. For example, at step225, event orchestration computing platform 110 may receive, via thecommunication interface (e.g., communication interface 115), from asecond client computing device (e.g., client computing device 165),second event definition information defining a second event, and thesecond event definition information may include second stimulusselection information associated with the second event. The second eventdefinition information defining the second event to be orchestrated byevent orchestration computing platform 110 and the second stimulusselection information associated with the second event may, forinstance, be received via an event definition user interface generatedby user interface computing platform 120 and sent to client computingdevice 165 by event orchestration computing platform 110 (e.g., the userinterface sent by event orchestration computing platform 110 to clientcomputing device 165 at step 224). In addition, the second stimulusselection information associated with the second event may, for example,identify one or more specific stimulus options specified by the user ofclient computing device 165 to be offered to the recipient of the newevent as incentives to receive funds associated with the new event via aparticular delivery method corresponding to the one or more specificstimulus options specified by the user of client computing device 165.For example, the second stimulus selection information associated withthe second event may, for example, identify and/or specify that therecipient of the new event should be prompted to select whether toreceive funds associated with the new event in a new account maintainedby a financial institution operating event orchestration computingplatform 110 or a different financial institution, via a prepaid debitcard usable via one or more debit networks, via a gift card that isredeemable with and/or otherwise usable with a merchant client or othertreasury client using client computing device 165 to define the newevent, and/or via one or more other delivery methods associated withother stimulus options.

In some embodiments, receiving the second event definition informationdefining the second event may include receiving information defining oneor more parameters of the second event from the second client computingdevice. For example, in receiving the second event definitioninformation defining the second event, event orchestration computingplatform 110 may receive information defining one or more parameters ofthe second event from the second client computing device (e.g., clientcomputing device 165). For example, the second event definitioninformation defining the second event to be orchestrated by eventorchestration computing platform 110 (which may, e.g., be received byevent orchestration computing platform 110 from client computing device165 at step 225) may include one or more parameters and/or otherinformation specified by a user of client computing device 165. Forexample, the second event to be orchestrated by event orchestrationcomputing platform 110 may be a payment transaction, and the one or moreparameters and/or other information specified by the user of clientcomputing device 165 may identify a recipient of the transaction to bepaid, an amount to be paid to the recipient of the transaction, whetherthe transaction has a single occurrence or multiple occurrences, and/orother characteristics of the transaction.

In some embodiments, the information defining the one or more parametersof the second event may include information defining the second event asa single event having a single occurrence. For example, the informationdefining the one or more parameters of the second event (which may,e.g., be received by event orchestration computing platform 110 fromclient computing device 165) may include information defining the secondevent as a single event having a single occurrence. For instance, thesecond event may correspond to a new payment transaction involving asingle payment to an identified recipient. In some embodiments, theinformation defining the one or more parameters of the second event mayinclude information defining the second event as a recurring eventhaving multiple occurrences. For example, the information defining theone or more parameters of the second event (which may, e.g., be receivedby event orchestration computing platform 110 from client computingdevice 165) may include information defining the second event as arecurring event having multiple occurrences. For instance, the secondevent may correspond to a new payment transaction involving multiplerecurring payments to an identified recipient.

At step 226, event orchestration computing platform 110 may generate anevent notification. For example, at step 226, event orchestrationcomputing platform 110 may generate an event notification for recipientcomputing device 175 based on receiving event definition informationfrom client computing device 165 identifying an alias linked torecipient computing device 175 as a recipient associated with the eventdefined by the event definition information received from clientcomputing device 165. At step 227, event orchestration computingplatform 110 may send the event notification to recipient computingdevice 175. In sending the event notification to recipient computingdevice 175, event orchestration computing platform 110 may, forinstance, send the event notification to recipient computing device 175via a push notification service associated with an operating systemexecuting on recipient computing device 175. Additionally oralternatively, in sending the event notification to recipient computingdevice 175, event orchestration computing platform 110 may send anelectronic mail message, a short message service message, and/or anothertype of electronic message to recipient computing device 175.

At step 228, event orchestration computing platform 110 may receive arequest for a delivery selection user interface (which may, e.g., alsobe referred to as a recipient-selection user interface) from recipientcomputing device 175. For example, at step 228, event orchestrationcomputing platform 110 may receive, via the communication interface(e.g., communication interface 115), from a second recipient computingdevice associated with the second event (e.g., recipient computingdevice 175), a second request for a recipient-selection user interface.For instance, event orchestration computing platform 110 may receivesuch a request after recipient computing device 175 sends the request inresponse to receiving a selection or other user input in response topresenting the event notification received from event orchestrationcomputing platform 110.

In some embodiments, the second recipient computing device associatedwith the second event may be linked to a second alias identified as arecipient in the second event definition information. For example, thesecond recipient computing device associated with the second event(e.g., recipient computing device 175) may be linked to a second aliasidentified as a recipient in the second event definition information(which may, e.g., be received by event orchestration computing platform110 from client computing device 165). In some instances, the secondalias identified as the recipient in the second event definitioninformation (which may, e.g., be received by event orchestrationcomputing platform 110 from client computing device 165) may include anemail address. For example, the second alias identified as the recipientin the second event definition information received by eventorchestration computing platform 110 from client computing device 165may include an email address that is linked to, registered with, and/orotherwise associated with the second recipient computing deviceassociated with the second event (e.g., recipient computing device 175)as an alias of the second recipient computing device associated with thesecond event (e.g., recipient computing device 175). Additionally oralternatively, the second alias identified as the recipient in thesecond event definition information (which may, e.g., be received byevent orchestration computing platform 110 from client computing device165) may include a mobile telephone number. For example, the secondalias identified as the recipient in the second event definitioninformation received by event orchestration computing platform 110 fromclient computing device 165 may include a mobile telephone number thatis linked to, registered with, and/or otherwise associated with thesecond recipient computing device associated with the second event(e.g., recipient computing device 175) as an alias of the secondrecipient computing device associated with the second event (e.g.,recipient computing device 175).

Referring to FIG. 2H, at step 229, event orchestration computingplatform 110 may identify one or more stimulus options available for auser of recipient computing device 175. For example, at step 229, basedon receiving the second request for the recipient-selection userinterface from the second recipient computing device associated with thesecond event (e.g., recipient computing device 175), event orchestrationcomputing platform 110 may identify one or more stimulus optionsavailable for a second user of the second recipient computing deviceassociated with the second event (e.g., recipient computing device 175)based on the second stimulus selection information associated with thesecond event. In identifying the one or more stimulus options availablefor the second user of the second recipient computing device associatedwith the second event (e.g., recipient computing device 175), eventorchestration computing platform 110 may, for example, select one ormore stimulus options to be offered to the second user of the secondrecipient computing device associated with the second event (e.g.,recipient computing device 175) based on the stimulus selectioninformation associated with the second event received from clientcomputing device 165, based on user profile information corresponding tothe recipient and/or another user of recipient computing device 175,and/or other factors. For example, certain stimulus options may beavailable to a particular user or a particular group of users, andother, different stimulus options may be available to a different useror a different group of users.

In some embodiments, identifying the one or more stimulus optionsavailable for the second user of the second recipient computing deviceassociated with the second event may include identifying at least onestimulus option as available for the second user of the second recipientcomputing device associated with the second event based on the at leastone stimulus option being specified by a user of the second clientcomputing device in the second stimulus selection information associatedwith the second event. For example, in identifying the one or morestimulus options available for the second user of the second recipientcomputing device associated with the second event (e.g., recipientcomputing device 175), event orchestration computing platform 110 mayidentify at least one stimulus option as available for the second userof the second recipient computing device associated with the secondevent (e.g., recipient computing device 175) based on the at least onestimulus option being specified by a user of the second client computingdevice (e.g., client computing device 165) in the second stimulusselection information associated with the second event. For instance,event orchestration computing platform 110 may identify and/or otherwiseselect one or more particular stimulus options to be offered that werespecified by the user of client computing device 165 in the eventdefinition information for the particular event received by eventorchestration computing platform 110 from client computing device 165.

At step 230, event orchestration computing platform 110 may generate oneor more commands directing user interface computing platform 120 togenerate a delivery selection user interface. For example, at step 230,event orchestration computing platform 110 may generate one or morecommands directing user interface computing platform 120 to generate adelivery selection user interface for recipient computing device 175that includes a dynamic stimulus option (e.g., based on identifying theone or more stimulus options available for the user of recipientcomputing device 175). For instance, the one or more commands generatedby event orchestration computing platform 110 may direct user interfacecomputing platform 120 to insert and/or include one or more controlsand/or other user interface elements in the delivery selection userinterface that are configured to offer and/or otherwise provide the oneor more stimulus options that were identified and/or otherwise selectedby event orchestration computing platform 110 for the user of recipientcomputing device 175. At step 231, event orchestration computingplatform 110 may send the one or more commands to user interfacecomputing platform 120 directing user interface computing platform 120to generate a delivery selection user interface. For example, at step231, event orchestration computing platform 110 may send, via thecommunication interface (e.g., communication interface 115), to a userinterface computing platform (e.g., user interface computing platform120), one or more commands directing the user interface computingplatform (e.g., user interface computing platform 120) to generate thedelivery selection user interface. The one or more commands generated byevent orchestration computing platform 110 and/or sent by eventorchestration computing platform 110 to user interface computingplatform 120 may include parameters and/or other information identifyingthe second recipient computing device associated with the second event(e.g., recipient computing device 175) and/or the entity identified asthe recipient for the second event (e.g., a registered and/or authorizeduser of recipient computing device 175), parameters and/or otherinformation identifying the user interface that is requested (e.g., oneor more parameters directing and/or causing user interface computingplatform 120 to include the identified stimulus options in the deliveryselection user interface), and/or other parameters and information.

At step 232, event orchestration computing platform 110 may receive adelivery selection user interface generated by user interface computingplatform 120 from user interface computing platform 120. For example, atstep 232, event orchestration computing platform 110 may receive, viathe communication interface (e.g., communication interface 115), fromthe user interface computing platform (e.g., user interface computingplatform 120), the delivery selection user interface. For instance, atstep 232, event orchestration computing platform 110 may receive fromuser interface computing platform 120 a user interface generated by userinterface computing platform 120 based on the one or more commands sentto user interface computing platform 120 by event orchestrationcomputing platform 110.

Referring to FIG. 2I, at step 233, event orchestration computingplatform 110 may send the delivery selection user interface generated byuser interface computing platform 120 to recipient computing device 175.For example, at step 233, based on identifying the one or more stimulusoptions available for the second user of the second recipient computingdevice associated with the second event (e.g., recipient computingdevice 175), event orchestration computing platform 110 may send, viathe communication interface (e.g., communication interface 115), to thesecond recipient computing device associated with the second event(e.g., recipient computing device 175), a second delivery selection userinterface. In addition, the second delivery selection user interface mayinclude a second user-selectable component that, when invoked, causesthe computing platform (e.g., event orchestration computing platform110) to create a second new endpoint associated with a second stimulusoption of the one or more stimulus options identified as being availablefor the second user of the second recipient computing device associatedwith the second event (e.g., recipient computing device 175). Forinstance, the delivery selection user interface generated by userinterface computing platform 120 and sent to recipient computing device175 by event orchestration computing platform 110 may include auser-selectable component (e.g., a button, a hyperlink, a pull-downmenu, and/or the like) that, when invoked, causes event orchestrationcomputing platform 110 to create a new endpoint associated with aspecific user-selected stimulus option of the one or more stimulusoptions identified as being available for the user of recipientcomputing device 175.

In sending the second delivery selection user interface to the secondrecipient computing device associated with the second event (e.g.,recipient computing device 175), event orchestration computing platform110 may cause recipient computing device 175 to display and/or otherwisepresent the user interface generated by user interface computingplatform 120 based on the one or more commands sent to user interfacecomputing platform 120 by event orchestration computing platform 110.For example, in sending the second delivery selection user interface tothe second recipient computing device associated with the second event(e.g., recipient computing device 175), event orchestration computingplatform 110 may cause recipient computing device 175 to display and/orotherwise present a graphical user interface similar to graphical userinterface 600, which is illustrated in FIG. 6. As seen in FIG. 6,graphical user interface 600 may include one or more fields, controls,and/or other elements that may allow a user of recipient computingdevice 175 to select and/or specify a delivery destination for thesecond event, such as a delivery destination for funds associated with across-border and/or cross-currency payment transaction event beingorchestrated by event orchestration computing platform 110. For example,graphical user interface 600 may include one or more fields, controls,and/or other elements that may allow a user of recipient computingdevice 175 to specify and/or otherwise define a destination parameterassociated with the event, a destination type parameter associated withthe event (which may, e.g., indicate a destination country and/or adestination currency for a cross-border and/or cross-currency paymenttransaction event), and/or other parameters associated with the newevent. In addition, graphical user interface 600 may include auser-selectable option (e.g., “Stimulus-Destination-2 | Other Options”)that, when invoked by the user of recipient computing device 175, causesevent orchestration computing platform 110 to create a new endpointassociated with a specific user-selected stimulus option of the one ormore stimulus options identified as being available for the user ofrecipient computing device 175. For example, graphical user interface600 may be configured to present the one or more stimulus optionsidentified as being available for the user of recipient computing device175 (e.g., in response to receiving input selecting “Other Options”)and/or may be configured to cause event orchestration computing platform110 to create a new endpoint associated with a particular optionselected by the user of recipient computing device 175 via graphicaluser interface 600 (e.g., “Stimulus-Destination-2”).

At step 234, event orchestration computing platform 110 may receivedelivery selection information from recipient computing device 175. Forexample, at step 234, event orchestration computing platform 110 mayreceive, via the communication interface (e.g., communication interface115), from the second recipient computing device associated with thesecond event (e.g., recipient computing device 175), second deliveryselection information. In addition, the second delivery selectioninformation (which may, e.g., be received by event orchestrationcomputing platform 110 from recipient computing device 175) may includeinformation indicating that the second user-selectable component hasbeen invoked. Further, the second delivery selection information (whichmay, e.g., be received by event orchestration computing platform 110from recipient computing device 175) may include information identifyingthe second new endpoint associated with the second stimulus option as asecond destination for the second event selected by the second user ofthe second recipient computing device associated with the second event(e.g., recipient computing device 175). For instance, eventorchestration computing platform 110 may receive from recipientcomputing device 175 delivery selection information that includesinformation indicating that the user-selectable component has beeninvoked (which may, e.g., cause event orchestration computing platform110 to create a new endpoint associated with a specific user-selectedstimulus option) and that further includes information identifying thenew endpoint (which may, e.g., be subsequently created by eventorchestration computing platform 110, as illustrated below) as thedestination that has been selected by the user of recipient computingdevice 175 to be the destination for the particular event.

At step 235, event orchestration computing platform 110 may validate thedelivery selection information received from recipient computing device175. For example, at step 235, event orchestration computing platform110 may validate the delivery selection information received from therecipient computing device (e.g., recipient computing device 175). Invalidating the delivery selection information received from therecipient computing device (e.g., recipient computing device 175), eventorchestration computing platform 110 may, for example, execute and/orapply one or more risk analysis evaluation algorithms, regulatorycompliance evaluation algorithms, account verification evaluationalgorithms, identity verification evaluation algorithms, and/or otheralgorithms to determine whether the delivery selection informationreceived from the recipient computing device (e.g., recipient computingdevice 175) is valid. If event orchestration computing platform 110determines that the delivery selection information received from therecipient computing device (e.g., recipient computing device 175) isinvalid, event orchestration computing platform 110 may generate and/orsend one or more error messages (e.g., to event recording computingplatform 130, client computing device 165, recipient computing device175, and/or one or more other systems and/or devices). Alternatively, ifevent orchestration computing platform 110 determines that the deliveryselection information received from the recipient computing device(e.g., recipient computing device 175) is valid, the event sequence maycontinue to step 236 as illustrated in FIG. 2I.

At step 236, event orchestration computing platform 110 may create a newendpoint based on the delivery selection information received fromrecipient computing device 175. For example, at step 236, eventorchestration computing platform 110 may create a second new endpointassociated with a second stimulus option of the one or more stimulusoptions identified as being available for the second user of the secondrecipient computing device associated with the second event (e.g.,recipient computing device 175) in response to receiving the informationindicating that the second user-selectable component has been invoked.For instance, event orchestration computing platform 110 may create anew endpoint corresponding to the stimulus option that has been selectedby the user of recipient computing device 175, and the new endpoint maybe a new account maintained by a financial institution operating eventorchestration computing platform 110 or a different financialinstitution, a prepaid debit card usable via one or more debit networks,a gift card that is redeemable with and/or otherwise usable with amerchant client or other treasury client which defined the second event,and/or the like.

In some embodiments, creating the second new endpoint associated withthe second stimulus option of the one or more stimulus options mayinclude: generating one or more commands directing an event recordingcomputing platform to create at least one record corresponding to thesecond new endpoint for the second user of the second recipientcomputing device associated with the second event; and sending, via thecommunication interface, to the event recording computing platform, theone or more commands directing the event recording computing platform tocreate the at least one record corresponding to the second new endpointfor the second user of the second recipient computing device associatedwith the second event. For example, in creating the second new endpointassociated with the second stimulus option of the one or more stimulusoptions for the second user of the second recipient computing deviceassociated with the second event (e.g., recipient computing device 175),event orchestration computing platform 110 may generate one or morecommands directing an event recording computing platform (e.g., eventrecording computing platform 130) to create at least one recordcorresponding to the second new endpoint for the second user of thesecond recipient computing device associated with the second event(e.g., recipient computing device 175). In addition, event orchestrationcomputing platform 110 may send, via the communication interface (e.g.,communication interface 115), to the event recording computing platform(e.g., event recording computing platform 130), the one or more commandsdirecting the event recording computing platform (e.g., event recordingcomputing platform 130) to create the at least one record correspondingto the second new endpoint for the second user of the second recipientcomputing device associated with the second event (e.g., recipientcomputing device 175). For example, the new endpoint may be a newaccount maintained by a financial institution operating eventorchestration computing platform 110, such as a new foreign,cross-currency banking account or digital wallet account, and the atleast one record may include a unique identifier, initial balance,and/or other information associated with the new account being createdby event orchestration computing platform 110 in response to theinvocation of the dynamic stimulus option. In other examples, the newendpoint may be a new account maintained by a different financialinstitution than the financial institution operating event orchestrationcomputing platform 110, a prepaid debit card usable via one or moredebit networks, a gift card that is redeemable with and/or otherwiseusable with a merchant client or other treasury client which defined thesecond event, and/or the like. In these other instances, event recordingcomputing platform 130 also may create and/or maintain one or morerecords associated with the new endpoint (e.g., based on commandsgenerated and/or sent to event recording computing platform 130 by eventorchestration computing platform 110).

Referring to FIG. 2J, at step 237, event orchestration computingplatform 110 may generate one or more event orchestration commands. Forexample, at step 237, based on receiving the second delivery selectioninformation from the second recipient computing device associated withthe second event (e.g., recipient computing device 175), eventorchestration computing platform 110 may generate, based on the seconddelivery selection information, one or more second event orchestrationcommands directing an event processor (e.g., external event processor150) to execute one or more actions associated with the second event.For instance, event orchestration computing platform 110 may generateone or more commands directing and/or controlling external eventprocessor 150 to execute one or more actions associated with the secondevent, such as one or more actions that perform and/or complete apayment transaction corresponding to the second event. For example, theone or more commands generated by event orchestration computing platform110 may direct external event processor 150 (which may, e.g., beassociated with a particular digital wallet service, banking service, orthe like) to transfer funds to the new endpoint (which may, e.g., be anew account, a new prepaid debit card, a new gift card, and/or the like,corresponding to the selected stimulus option) created by eventorchestration computing platform 110 and selected by the user of thesecond recipient computing device associated with the second event(e.g., recipient computing device 175).

At step 238, event orchestration computing platform 110 may send the oneor more event orchestration commands to external event processor 150.For example, at step 238, event orchestration computing platform 110 maysend, via the communication interface (e.g., communication interface115), to the event processor (e.g., external event processor 150), theone or more second event orchestration commands directing the eventprocessor (e.g., external event processor 150) to execute the one ormore actions associated with the second event. In some instances, theevent processor (to which event orchestration computing platform 110may, e.g., send the one or more event orchestration commands) may be aninternal event processor (e.g., internal event processor 145) operatedby an entity operating the computing platform (e.g., event orchestrationcomputing platform 110). In other instances, the event processor (towhich event orchestration computing platform 110 may, e.g., send the oneor more event orchestration commands) may be an external event processor(e.g., external event processor 150, external event processor 155)operated by a third-party entity not associated with an entity operatingthe computing platform (e.g., event orchestration computing platform110). For example, event orchestration computing platform 110 may sendthe one or more event orchestration commands to such an external eventprocessor (e.g., external event processor 150, external event processor155) in instances in which the destination of the event (e.g., the newendpoint) is a new account with a financial institution different fromthe financial institution operating event orchestration computingplatform 110, a prepaid debit card associated with a debit networkprovided by a financial institution different from the financialinstitution operating event orchestration computing platform 110, amerchant gift card that is managed and/or processed by a financialinstitution different from the financial institution operating eventorchestration computing platform 110, and/or the like.

At step 239, event orchestration computing platform 110 may receiveconfirmation information from external event processor 150. For example,at step 239, event orchestration computing platform 110 may receive fromexternal event processor 150 confirmation information indicating thatone or more actions associated with the second event were performedand/or completed by one or more event servers (e.g., external eventprocessor 150 and/or related servers and/or systems). At step 240, eventorchestration computing platform 110 may send one or more updatecommands to event recording computing platform 130. For example, at step240, event orchestration computing platform 110 may send one or moreupdate commands to event recording computing platform 130 directingevent recording computing platform 130 to update one or more recordsindicating that the second event has been completed and/or that one ormore actions associated with the second event have been performed basedon the one or more event orchestration commands sent to external eventprocessor 150 by event orchestration computing platform 110 and/or basedon the confirmation information received by event orchestrationcomputing platform 110 from external event processor 150.

FIG. 7 depicts an illustrative method for multicomputer processing ofclient device request data using a centralized event orchestrator inaccordance with one or more example embodiments. Referring to FIG. 7, atstep 705, a computing platform having at least one processor, a memory,and a communication interface may receive, via the communicationinterface, from a first client computing device, first event definitioninformation defining a first event, and the first event definitioninformation may include first stimulus selection information associatedwith the first event. At step 710, the computing platform may receive,via the communication interface, from a first recipient computing deviceassociated with the first event, a first request for arecipient-selection user interface. At step 715, based on receiving thefirst request for the recipient-selection user interface from the firstrecipient computing device associated with the first event, thecomputing platform may identify one or more stimulus options availablefor a first user of the first recipient computing device associated withthe first event based on the first stimulus selection informationassociated with the first event.

At step 720, based on identifying the one or more stimulus optionsavailable for the first user of the first recipient computing deviceassociated with the first event, the computing platform may send, viathe communication interface, to the first recipient computing deviceassociated with the first event, a first delivery selection userinterface, and the first delivery selection user interface may include afirst user-selectable component that, when invoked, causes the computingplatform to create a first new endpoint associated with a first stimulusoption of the one or more stimulus options identified as being availablefor the first user of the first recipient computing device associatedwith the first event. At step 725, the computing platform may receive,via the communication interface, from the first recipient computingdevice associated with the first event, first delivery selectioninformation, and the first delivery selection information may includeinformation indicating that the first user-selectable component has beeninvoked, and the first delivery selection information may includeinformation identifying the first new endpoint associated with the firststimulus option as a first destination for the first event selected bythe first user of the first recipient computing device associated withthe first event. At step 730, based on receiving the first deliveryselection information from the first recipient computing deviceassociated with the first event, the computing platform may generate,based on the first delivery selection information, one or more firstevent orchestration commands directing an event processor to execute oneor more actions associated with the first event. At step 735, thecomputing platform may send, via the communication interface, to theevent processor, the one or more first event orchestration commandsdirecting the event processor to execute the one or more actionsassociated with the first event.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored as computer-readable instructions on a computer-readable mediumsuch as a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. The functionality of the program modules maybe combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may be and/or include one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, and thelike). For example, in alternative embodiments, one or more of thecomputing platforms discussed above may be combined into a singlecomputing platform, and the various functions of each computing platformmay be performed by the single computing platform. In such arrangements,any and/or all of the above-discussed communications between computingplatforms may correspond to data being accessed, moved, modified,updated, and/or otherwise used by the single computing platform.Additionally or alternatively, one or more of the computing platformsdiscussed above may be implemented in one or more virtual machines thatare provided by one or more physical computing devices. In sucharrangements, the various functions of each computing platform may beperformed by the one or more virtual machines, and any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the one or more virtual machines.

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A computing platform, comprising: at least oneprocessor; a communication interface communicatively coupled to the atleast one processor; and memory storing computer-readable instructionsthat, when executed by the at least one processor, cause the computingplatform to: receive, via the communication interface, from a firstclient computing device, first event definition information defining afirst event, the first event definition information comprising firststimulus selection information associated with the first event; receive,via the communication interface, from a first recipient computing deviceassociated with the first event, a first request for arecipient-selection user interface; based on receiving the first requestfor the recipient-selection user interface from the first recipientcomputing device associated with the first event, identify one or morestimulus options available for a first user of the first recipientcomputing device associated with the first event based on the firststimulus selection information associated with the first event; based onidentifying the one or more stimulus options available for the firstuser of the first recipient computing device associated with the firstevent, send, via the communication interface, to the first recipientcomputing device associated with the first event, a first deliveryselection user interface, the first delivery selection user interfacecomprising a first user-selectable component that, when invoked, causesthe computing platform to create a first new endpoint associated with afirst stimulus option of the one or more stimulus options identified asbeing available for the first user of the first recipient computingdevice associated with the first event; receive, via the communicationinterface, from the first recipient computing device associated with thefirst event, first delivery selection information, the first deliveryselection information comprising information indicating that the firstuser-selectable component has been invoked, and the first deliveryselection information comprising information identifying the first newendpoint associated with the first stimulus option as a firstdestination for the first event selected by the first user of the firstrecipient computing device associated with the first event; based onreceiving the first delivery selection information from the firstrecipient computing device associated with the first event, generate,based on the first delivery selection information, one or more firstevent orchestration commands directing an event processor to execute oneor more actions associated with the first event; and send, via thecommunication interface, to the event processor, the one or more firstevent orchestration commands directing the event processor to executethe one or more actions associated with the first event.
 2. Thecomputing platform of claim 1, wherein receiving the first eventdefinition information defining the first event comprises receivinginformation defining one or more parameters of the first event from thefirst client computing device.
 3. The computing platform of claim 2,wherein the information defining the one or more parameters of the firstevent comprises information defining the first event as a single eventhaving a single occurrence.
 4. The computing platform of claim 2,wherein the information defining the one or more parameters of the firstevent comprises information defining the first event as a recurringevent having multiple occurrences.
 5. The computing platform of claim 1,wherein the first recipient computing device associated with the firstevent is linked to a first alias identified as a recipient in the firstevent definition information.
 6. The computing platform of claim 5,wherein the first alias identified as the recipient in the first eventdefinition information comprises an email address.
 7. The computingplatform of claim 5, wherein the first alias identified as the recipientin the first event definition information comprises a mobile telephonenumber.
 8. The computing platform of claim 1, wherein identifying theone or more stimulus options available for the first user of the firstrecipient computing device associated with the first event comprisesidentifying at least one stimulus option as available for the first userof the first recipient computing device associated with the first eventbased on the at least one stimulus option being specified by a user ofthe first client computing device in the first stimulus selectioninformation associated with the first event.
 9. The computing platformof claim 1, wherein the event processor is an internal event processoroperated by an entity operating the computing platform.
 10. Thecomputing platform of claim 1, wherein the event processor is anexternal event processor operated by a third-party entity not associatedwith an entity operating the computing platform.
 11. The computingplatform of claim 1, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: receive, via thecommunication interface, from a second client computing device, secondevent definition information defining a second event, the second eventdefinition information comprising second stimulus selection informationassociated with the second event; receive, via the communicationinterface, from a second recipient computing device associated with thesecond event, a second request for a recipient-selection user interface;based on receiving the second request for the recipient-selection userinterface from the second recipient computing device associated with thesecond event, identify one or more stimulus options available for asecond user of the second recipient computing device associated with thesecond event based on the second stimulus selection informationassociated with the second event; based on identifying the one or morestimulus options available for the second user of the second recipientcomputing device associated with the second event, send, via thecommunication interface, to the second recipient computing deviceassociated with the second event, a second delivery selection userinterface, the second delivery selection user interface comprising asecond user-selectable component that, when invoked, causes thecomputing platform to create a second new endpoint associated with asecond stimulus option of the one or more stimulus options identified asbeing available for the second user of the second recipient computingdevice associated with the second event; receive, via the communicationinterface, from the second recipient computing device associated withthe second event, second delivery selection information, the seconddelivery selection information comprising information indicating thatthe second user-selectable component has been invoked, and the seconddelivery selection information comprising information identifying thesecond new endpoint associated with the second stimulus option as asecond destination for the second event selected by the second user ofthe second recipient computing device associated with the second event;based on receiving the second delivery selection information from thesecond recipient computing device associated with the second event,generate, based on the second delivery selection information, one ormore second event orchestration commands directing the event processorto execute one or more actions associated with the second event; andsend, via the communication interface, to the event processor, the oneor more second event orchestration commands directing the eventprocessor to execute the one or more actions associated with the secondevent.
 12. The computing platform of claim 11, wherein receiving thesecond event definition information defining the second event comprisesreceiving information defining one or more parameters of the secondevent from the second client computing device.
 13. The computingplatform of claim 12, wherein the information defining the one or moreparameters of the second event comprises information defining the secondevent as a single event having a single occurrence.
 14. The computingplatform of claim 12, wherein the information defining the one or moreparameters of the second event comprises information defining the secondevent as a recurring event having multiple occurrences.
 15. Thecomputing platform of claim 11, wherein the second recipient computingdevice associated with the second event is linked to a second aliasidentified as a recipient in the second event definition information.16. The computing platform of claim 15, wherein the second aliasidentified as the recipient in the second event definition informationcomprises an email address.
 17. The computing platform of claim 15,wherein the second alias identified as the recipient in the second eventdefinition information comprises a mobile telephone number.
 18. Thecomputing platform of claim 11, wherein identifying the one or morestimulus options available for the second user of the second recipientcomputing device associated with the second event comprises identifyingat least one stimulus option as available for the second user of thesecond recipient computing device associated with the second event basedon the at least one stimulus option being specified by a user of thesecond client computing device in the second stimulus selectioninformation associated with the second event.
 19. A method, comprising:at a computing platform comprising at least one processor, memory, and acommunication interface: receiving, by the at least one processor, viathe communication interface, from a first client computing device, firstevent definition information defining a first event, the first eventdefinition information comprising first stimulus selection informationassociated with the first event; receiving, by the at least oneprocessor, via the communication interface, from a first recipientcomputing device associated with the first event, a first request for arecipient-selection user interface; based on receiving the first requestfor the recipient-selection user interface from the first recipientcomputing device associated with the first event, identifying, by the atleast one processor, one or more stimulus options available for a firstuser of the first recipient computing device associated with the firstevent based on the first stimulus selection information associated withthe first event; based on identifying the one or more stimulus optionsavailable for the first user of the first recipient computing deviceassociated with the first event, sending, by the at least one processor,via the communication interface, to the first recipient computing deviceassociated with the first event, a first delivery selection userinterface, the first delivery selection user interface comprising afirst user-selectable component that, when invoked, causes the computingplatform to create a first new endpoint associated with a first stimulusoption of the one or more stimulus options identified as being availablefor the first user of the first recipient computing device associatedwith the first event; receiving, by the at least one processor, via thecommunication interface, from the first recipient computing deviceassociated with the first event, first delivery selection information,the first delivery selection information comprising informationindicating that the first user-selectable component has been invoked,and the first delivery selection information comprising informationidentifying the first new endpoint associated with the first stimulusoption as a first destination for the first event selected by the firstuser of the first recipient computing device associated with the firstevent; based on receiving the first delivery selection information fromthe first recipient computing device associated with the first event,generating, by the at least one processor, based on the first deliveryselection information, one or more first event orchestration commandsdirecting an event processor to execute one or more actions associatedwith the first event; and sending, by the at least one processor, viathe communication interface, to the event processor, the one or morefirst event orchestration commands directing the event processor toexecute the one or more actions associated with the first event.
 20. Oneor more non-transitory computer-readable media storing instructionsthat, when executed by a computing platform comprising at least oneprocessor, memory, and a communication interface, cause the computingplatform to: receive, via the communication interface, from a firstclient computing device, first event definition information defining afirst event, the first event definition information comprising firststimulus selection information associated with the first event; receive,via the communication interface, from a first recipient computing deviceassociated with the first event, a first request for arecipient-selection user interface; based on receiving the first requestfor the recipient-selection user interface from the first recipientcomputing device associated with the first event, identify one or morestimulus options available for a first user of the first recipientcomputing device associated with the first event based on the firststimulus selection information associated with the first event; based onidentifying the one or more stimulus options available for the firstuser of the first recipient computing device associated with the firstevent, send, via the communication interface, to the first recipientcomputing device associated with the first event, a first deliveryselection user interface, the first delivery selection user interfacecomprising a first user-selectable component that, when invoked, causesthe computing platform to create a first new endpoint associated with afirst stimulus option of the one or more stimulus options identified asbeing available for the first user of the first recipient computingdevice associated with the first event; receive, via the communicationinterface, from the first recipient computing device associated with thefirst event, first delivery selection information, the first deliveryselection information comprising information indicating that the firstuser-selectable component has been invoked, and the first deliveryselection information comprising information identifying the first newendpoint associated with the first stimulus option as a firstdestination for the first event selected by the first user of the firstrecipient computing device associated with the first event; based onreceiving the first delivery selection information from the firstrecipient computing device associated with the first event, generate,based on the first delivery selection information, one or more firstevent orchestration commands directing an event processor to execute oneor more actions associated with the first event; and send, via thecommunication interface, to the event processor, the one or more firstevent orchestration commands directing the event processor to executethe one or more actions associated with the first event.